DB2-Resource not available or operator intervention.: 57033 - [IBM][CLI Driver][DB2/NT] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "68".

Notes/Domino 8 Forum

Subject: DB2-Resource not available or operator intervention.: 57033 - [IBM][CLI Driver][DB2/NT] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "68".

Feedback Type: Problem

Product Area: Domino Server

Technical Area: New Features

Platform: Windows 2003 server

Release: 8.0.1

Reproducible: Always

I am trying to convert a database to use DB2 to store data using "load compact -p". The database is 361 MB and 232,000 documents. The conversion will run about 7 hours and then end with a message like this:

02/26/2008 12:52:49 AM ServerName/Org
Failed when DB2 was getting properties. DB2-Resource not available or operator intervention.: 57033 - [IBM][CLI Driver][DB2/NT] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "68". SQLSTATE=57033 - 192.168.1.22.19466.080226023816(ncompact)
02/26/2008 12:52:49 AM Deadlock detected.: An error occurred accessing the db2 datasource.
02/26/2008 12:52:49 AM DB2 Deferred processing task purging data in group GRP1 and schema SCF71757
02/26/2008 12:52:49 AM Error compacting databasepath.nsf: Invalid arguments

I've tried this twice now with he same result. The explanation I found for that error does not help because I have no control over the frequency of the commits. I am using using DB2 9.1.

SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "<reason-code>".

Explanation: The request issued was involved in an unresolved contention for use of an object and the execution failed.

The reason codes are as follows:

2 transaction branch failed due to deadlock.

68 transaction branch failed due to lock timeout.

72 transaction rolled back due to an error concerning a DB2 Data Links Manager involved in the transaction.

80 statement failed due to timeout.

User Response:

For reason code 80, you can retry the failed statement without terminating the application. If the application accesses multiple remote databases, it may be better to rollback the transaction to avoid the possibility of a global deadlock.
For other reason codes, issue a request to rollback the transaction. The transaction cannot be commited due to the failure of the current transaction branch.
To help avoid deadlock or lock timeout, issue frequent COMMIT operations, if possible, within long-running applications or applications requiring data with high concurrent access.

Thanks
Steve

Feedback number SDAS7C7NGR created by ~Julia Cisgeromangon on 02/26/2008